Refresh README and docs output examples for v0.2#8
Conversation
Update the embedded output examples to match what extraction actually
produces:
- publisher and publicationYear shown as null (platform-owned, set at publish)
- rightsList removed (stripped from output); publisher dropped from the ROR
canonicalisation note and the pipeline-uses list
- descriptionType shown as Other (set deterministically; no longer asked of
the model)
- affiliation identifier casing corrected to schemeURI
- formats added (derived from the file extension)
- architecture caption examples fixed to the {id, caption} shape
Docs only; patch bump to 0.9.23.
|
Thank you for submitting this pull request! We appreciate your contribution to the project. Before we can merge it, we need to review the changes you've made to ensure they align with our code standards and meet the requirements of the project. We'll get back to you as soon as we can with feedback. Thanks again! |
Reviewer's guide (collapsed on small PRs)Reviewer's GuideUpdates README and architecture docs examples so they align with the current extraction behavior, including null publisher/publicationYear, deterministic descriptionType, removal of rightsList/SPDX mentions, corrected ROR schemeURI casing, added formats, corrected caption shapes, and bumps version to 0.9.23. Entity relationship diagram for updated poster JSON output fieldserDiagram
Poster {
int publicationYear
json publisher
string descriptionType
string formats
}
Poster ||--o{ Description : has
Description {
string description
string descriptionType
}
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
|
Thanks for making updates to your pull request. Our team will take a look and provide feedback as soon as possible. Please wait for any GitHub Actions to complete before editing your pull request. If you have any additional questions or concerns, feel free to let us know. Thank you for your contributions! |
There was a problem hiding this comment.
Hey - I've left some high level feedback:
- Double-check that the
schemeURIcasing change matches the actual JSON field name in all code paths and other docs/schema references, so we don't end up with mixedschemeUri/schemeURIusage.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- Double-check that the `schemeURI` casing change matches the actual JSON field name in all code paths and other docs/schema references, so we don't end up with mixed `schemeUri`/`schemeURI` usage.Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
|
Thank you for getting this pull request merged. We appreciate your contribution and look forward to your next one! |
Updates the embedded output examples in the README and architecture docs to match what extraction actually produces:
Docs only. Patch bump to 0.9.23.
Summary by Sourcery
Align documentation examples and field descriptions with the current extraction behaviour and bump the package patch version.
Enhancements:
Build:
Documentation: